Skip to content

limit mergify auto doc label#2519

Merged
dsikka merged 3 commits intomainfrom
chill_mergify_out
Mar 26, 2026
Merged

limit mergify auto doc label#2519
dsikka merged 3 commits intomainfrom
chill_mergify_out

Conversation

@HDCharles
Copy link
Copy Markdown
Collaborator

@HDCharles HDCharles commented Mar 25, 2026

Summary:

make mergify only auto label if there are ONLY
examples/docs changes rather than whenever there are examples/docs changes

Summary:

make mergify only auto label if there are ONLY
examples/docs changes rather than whenever there are
examples/docs changes

Signed-off-by: HDCharles <charlesdavidhernandez@gmail.com>
@github-actions
Copy link
Copy Markdown

👋 Hi! Thank you for contributing to llm-compressor. Please add the ready label when the PR is ready for review.

Note: This is required to complete the testing suite, please only add the label once the PR is code complete and local testing has been performed.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the accuracy of automated labeling within the repository by modifying the Mergify configuration. The change ensures that the 'auto doc' label is applied only to pull requests that are solely focused on documentation or example updates, preventing its application to PRs that also include changes to core functional code, testing suites, or CI/CD workflows.

Highlights

  • Mergify Auto-Labeling Logic: The Mergify configuration has been updated to refine when the 'auto doc' label is applied. Previously, the label was added if any documentation or example files were changed. Now, it will only be applied if all changes are exclusively within documentation, examples, or top-level markdown files, explicitly excluding modifications to source code, tests, or GitHub workflow files.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@HDCharles HDCharles added the ready When a PR is ready for review label Mar 25, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the Mergify configuration to refine the documentation label application by adding exclusions for src/, tests/, and .github/workflows/ directories. The review suggests that these exclusions are incomplete and could still lead to incorrect labeling for changes involving the Mergify configuration file itself, Makefile, or pyproject.toml, proposing a broader set of exclusions to prevent incorrect labeling.

HDCharles and others added 2 commits March 25, 2026 15:32
Updated Mergify configuration to include .github and specific files.

Signed-off-by: HDCharles <39544797+HDCharles@users.noreply.github.com>
@dsikka dsikka enabled auto-merge (squash) March 26, 2026 01:32
Copy link
Copy Markdown
Collaborator

@brian-dellabetta brian-dellabetta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@dsikka dsikka merged commit 437f8af into main Mar 26, 2026
14 checks passed
@dsikka dsikka deleted the chill_mergify_out branch March 26, 2026 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready When a PR is ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants